MailDoor User's Guide
Troubleshooting
As a general troubleshooting aid, you should consider sending a test message to the desired e-mail address on your AIMS server and following its path. If everything is working successfully, you should momentarily see the message appear in the MailDoor input folder, then dissappear once MailDoor has forwarded the message.
While troubleshooting, keep in mind that many of the problems encountered with MailDoor may actually be due to incorrect set up of AIMS. In addition to the hints indicated here, be sure to consult the AIMS documentation for additional advice. Also, checking the AIMS mail log may provide some clues.
Mail to all MailDoor accounts is not being forwarded.
- Make sure that MailDoor is running.
- Make sure the "Save as files..." pathname you have entered in AIMS for your MailDoor accounts points to the input folder you have selected in MailDoor. You can check (and change) the path to MailDoor's input folder using the Preferences menu item.
- Make sure this pathname entered in AIMS does not end with a colon.
Mail to a specific MailDoor account is not being forwarded
- Make sure the "Save as files..." option in AIMS for this account is selected and that the pathname you have entered points to the input folder you have selected in MailDoor.
- Make sure this pathname does not end with a colon.
- Make sure the specific MailDoor account has been configured into the appropriate domains' forwarding lists in MailDoor.
All mail for a specific domain is not being forwarded
- Check to make sure that the domain name has been entered into the "Server names" part of the AIMS Preferences dialog, and that AIMS has been restarted after entering that domain name.
- Check to make sure that an appropriate MX record for the domain has been set up in the domain name server (DNS) for that domain. The MX record must point to AIMS as the server to handle mail for that domain. See Appendix 2.
- Make sure the domain name has been configured into MailDoor.
Mail sent to the server's own domain is not being forwarded
- The server's own domain works just like any other MailDoor domain. Be sure you have configured the server's own domain into MailDoor, and that you have set up all the desired MailDoor accounts for that domain.
Mail sent to accounts which have not been specifically set up in AIMS is not being forwarded, even though I've enabled the "Forward all other mail for domain" option in MailDoor for the domains where such forwarding is desired.
- Check to make sure that you have enabled the "<Any-name>" account in AIMS, and set the "Save as files..." option and the correct pathname.
Mail sent to one domain is delivered to an account by the same name in another domain, even though that account is not configured as a MailDoor account.
- Accounts not set up as MailDoor accounts (that is, using the "Save as files..." forwarding option) will receive mail sent to any domain name which AIMS has been configured to accept mail for. If you believe mail will be sent to the same account name in more than one domain, and want that mail processed differently for each domain, you must set that account up as a MailDoor account.
A large number of old mail files are building up in the MailDoor input folder.
- Be sure that MailDoor is running.
- Be sure that you have correctly configured MailDoor with a "no such recipient" (NSR) account. If MailDoor cannot otherwise forward a particular piece of mail, it will forward that mail to the NSR account. If no NSR account has been configured, the mail will remain in the MailDoor input folder.
- Be sure you do not have a mail forwarding loop, where one MailDoor account is set up to forward to another MailDoor or to an AIMS account which in turn forwards the mail back to the first MailDoor account.
Back to Table of Contents
Back to MailDoor Reference
Forward to Appendix 1